Cross-pollination of multiple sync sources

ABSTRACT

The present invention allows a user to synchronize a device with at least two data sources that may cross-pollinate. The user&#39;s device is used to shuttle changes between the sources and resolves conflicts when changes are made to an item on multiple sources concurrently. The user&#39;s device keeps track of which version of the item each sync source has and synchronizes each of the sources to the latest version of an item.

BACKGROUND OF THE INVENTION

Users can synchronize (“sync”) one device with another. For example, auser may synchronize their work computer to their mobile device. Aftersynchronization the mobile device and the computer include the sameinformation that was selected to be synchronized. The basic goal ofsynchronization is to keep two systems current with each other. Changesthat are made to one source are propagated to the other when the devicessync.

For example, when a user syncs their Contacts on their mobile devicewith their Home PC, then the home PC and the mobile device will have thesame contacts after the synchronization has completed. Many users syncitems including their email, contacts, calendar, as well as documents.It can be very difficult, however, to sync information between more thantwo different devices. What is needed is a way to sync with multiplesync sources.

SUMMARY OF THE INVENTION

The present invention is directed towards synchronizing a device withmore than one computing device (a “sync source”).

According to one aspect of the invention, the devices “cross-pollinate”their data. One of the computing devices, such as the mobile device,tracks which version of the item each data source has and synchronizesthe data source to the latest version of an item. The users canselectively enable and disable cross-pollination for items and datasources.

According to another aspect of the invention, a duplicate detectionalgorithm helps to avoid the generation of duplicate data across thedevices.

According to yet another aspect, deleting an item may be handleddifferently depending on the differentiation of deleted items ascompared to items that are no longer in a user's filter.

According to still yet another aspect, cross-pollination may occur eventhough the sync sources utilize different versions of the sync protocol.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 and 2 illustrate exemplary computing devices that may be used inone exemplary embodiment of the present invention;

FIG. 3 shows a cross-pollination sync system;

FIG. 4 illustrates enabling and disabling cross-pollination;

FIG. 5 illustrates an exemplary sync table architecture;

FIG. 6 illustrates a soft delete and a hard delete;

FIG. 7 illustrates processing a command to add an item to the device;

FIG. 8 illustrates an exemplary duplicate detection scenario;

FIG. 9 shows processing an add command for a duplicate of an existingitem on the Device;

FIG. 10 illustrates cross-pollinating a v1 and v3 server;

FIGS. 11 and 12 show exemplary synchronization scenarios;

FIG. 13 illustrates Data Source Creation;

FIG. 14 shows a process for removing a data source; and

FIG. 15 illustrates reconciling data source information that is out ofsync , in accordance with aspects of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Throughout the specification and claims, the following terms take themeanings explicitly associated herein, unless the context clearlydictates otherwise. The term “cross-pollination” refers to mixing orco-mingling data from multiple sync sources.

Illustrative Operating Environment

With reference to FIG. 1, one exemplary system for implementing theinvention includes a computing device, such as computing device 100. Ina very basic configuration, computing device 100 typically includes atleast one processing unit 102 and system memory 104. Depending on theexact configuration and type of computing device, system memory 104 maybe volatile (such as RAM), non-volatile (such as ROM, flash memory,etc.) or some combination of the two. System memory 104 typicallyincludes an operating system 105, one or more applications 106, and mayinclude program data 107. In one embodiment, application 106 may includea sync application 120. This basic configuration is illustrated in FIG.1 by those components within dashed line 108.

Computing device 100 may have additional features or functionality. Forexample, computing device 100 may also include additional data storagedevices (removable and/or non-removable) such as, for example, magneticdisks, optical disks, or tape. Such additional storage is illustrated inFIG. 1 by removable storage 109 and non-removable storage 110. Computerstorage media may include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer readable instructions, data structures,program modules, or other data. System memory 104, removable storage 109and non-removable storage 110 are all examples of computer storagemedia. Computer storage media includes, but is not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by computing device 100. Any such computerstorage media may be part of device 100. Computing device 100 may alsohave input device(s) 112 such as keyboard, mouse, pen, voice inputdevice, touch input device, etc. Output device(s) 114 such as a display,speakers, printer, etc. may also be included.

Computing device 100 may also contain communication connections 116 thatallow the device to communicate with other computing devices 118, suchas over a network. Communication connection 116 is one example ofcommunication media. Communication media may typically be embodied bycomputer readable instructions, data structures, program modules, orother data in a modulated data signal, such as a carrier wave or othertransport mechanism, and includes any information delivery media. Theterm “modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media. The term computer readable media as used herein includesboth storage media and communication media.

FIG. 2 illustrates a mobile computing device that may be used in oneexemplary embodiment of the present invention. With reference to FIG. 2,one exemplary system for implementing the invention includes a mobilecomputing device, such as mobile computing device 200. Mobile computingdevice 200 includes processor 260, memory 262, display 228, and keypad232. Memory 262 generally includes both volatile memory (e.g., RAM) andnon-volatile memory (e.g., ROM, Flash Memory, or the like). Mobilecomputing device 200 includes operating system 264, such as the WindowsCE operating system from Microsoft Corporation, or another operatingsystem, which is resident in memory 262 and executes on processor 260.Keypad 232 may be a push button numeric dialing pad (such as on atypical telephone), a multi-key keyboard (such as a conventionalkeyboard). Display 228 may be a liquid crystal display, or any othertype of display commonly used in mobile computing devices. Display 228may be touch-sensitive, and would then also act as an input device.

One or more application programs 266 are loaded into memory 262 and runon the operating system 264. A syncing application resides on mobilecomputing device 200 and is programmed to perform syncing applications.The syncing application may reside in the hardware or software of thedevice. Mobile computing device 200 also includes non-volatile storage268 within memory 262. Non-volatile storage 268 may be used to storepersistent information which should not be lost if mobile computingdevice 200 is powered down.

Mobile computing device 200 includes power supply 270, which may beimplemented as one or more batteries. Power supply 270 might furtherinclude an external power source, such as an AC adapter or a powereddocking cradle that supplements or recharges the batteries.

Mobile computing device 200 is shown with two types of optional externalnotification mechanisms: LED 240 and audio interface 274. These devicesmay be directly coupled to power supply 270 so that when activated, theyremain on for a duration dictated by the notification mechanism eventhough processor 260 and other components might shut down to conservebattery power. Audio interface 274 is used to provide audible signals toand receive audible signals from the user. For example, audio interface274 may be coupled to a speaker for providing audible output and to amicrophone for receiving audible input, such as to facilitate atelephone conversation.

Mobile computing device 200 also includes wireless interface layer 272that performs the function of transmitting and receiving communications.The wireless interface layer 272 facilitates wireless connectivitybetween the mobile computing device 200 and the outside world. Accordingto one embodiment, transmissions to and from the wireless interfacelayer 272 are conducted under control of the operating system 264. Inother words, communications received by wireless interface layer 272 maybe disseminated to application programs 266 via operating system 264,and vice versa.

Cross-Pollination of Multiple Sync Sources

FIG. 3 shows a cross-pollination sync system, in accordance with aspectsof the invention. Users can sync a computing device, such as Device 1(305), with more than one computing device that are each considered a“sync source.”

In an exemplary cross-pollination scenario, a user typically has asingle device that is synced with two sync sources. The usersynchronizes the device with both sources and cross-pollination keepsthe sources in sync with each other. The user's device is used toshuttle changes between the sources and resolves conflicts when changesare made to an item on multiple sources concurrently. The user's devicekeeps track of which version of the item each sync source has andsynchronizes each of the sources to the latest version of an item.

As an example of cross-pollination, suppose a user syncs their PDAdevice (305) with a Home PC (315) and also with a work PC (310). Oncesynchronized, each of the devices (the PDA device 305, Work PC 310, andHome PC 315) will include Item A 320. When the user syncs their PDA withthe Work PC, Item A is received by the PDA. When the user syncs the PDAwith the Home PC, then Item A that came to the PDA from the Work PC willautomatically be sent to the Home PC. Additionally, any items that werecreated on the Home PC will be automatically sent to the Work PC throughthe PDA when cross-pollination is enabled.

According to one embodiment, users may enable and disablecross-pollination between the sources. In other words, users are able tocross-pollinate between the sources or keep items separate. Thiscross-pollinate setting can be switched on and off at any time. Forexample, the user may turn off the ability to cross-pollinate with theHome PC (315). When cross-pollination is disabled to the Home PC, itemsfrom the Work PC will not move to the Home PC. In addition, a user couldhave one source kept separate and two other sources cross-pollinating.This flexibility aids in allowing the user to take total control of howdata is synchronized.

According to one embodiment, when the device is no longer synchronizingwith a single source, then all of the data is purged from the device.The data may also be left on the device. When the device is syncing withtwo or more sources, then the data is left on the device since it issyncing with another source. The ID column is cleared for the datasource not being synchronized with and the tracking data for that sourceis removed.

FIG. 4 illustrates enabling and disabling cross-pollination, inaccordance with aspects of the invention. Cross-pollination sync devicesare aware of the sources they are syncing with. According to oneembodiment, the sync source configuration information is stored on themobile device and utilizes the AirSync protocol. The configurationinformation may be stored at other locations and the devices may utilizeother sync protocols.

According to one embodiment, administrators set policies on the deviceto limit the number of sources the device can sync with. This featurecan be used to block cross-pollination by limiting the sources a devicecan sync with to a predetermined number. According to other embodiments,any authorized user may set the policies on the device.

Example 1 shows syncing one data source (Work PC 310) with PDA 305. Ascan be seen Item A is replicated on both devices.

Example 2 shows adding a second data source (Home PC 315). PDA 305 syncswith both the work PC and the home PC and each device includes each ofthe items on all of the devices. Item A, which originally was on thework PC is replicated to PDA 305 and the home PC. Item B, whichoriginally was on the home PC is replicated to PDA 305 and the work PC.

Example 3 illustrates changing the sync settings to sync items with theWork PC that are created on the device and to not allow the Work PC andthe Home PC to cross-pollinate. As can be seen, item C that was createdon the device has synced with the Work PC but has not cross-pollinatedto the Home PC.

Example 4 shows items created on the device sync to the Work PC andnewly created items created on the home PC doe not cross-pollinate tothe Work PC. In this example, item D was created on the Home PC andsynced with the device, but not the Work PC.

Example 5 illustrates changing the sync settings to cross-pollinatenewly created items across all of the devices. In this example, item Ewas created on the work PC and synced with the device and the home PC.According to one embodiment, items that are created under different syncsettings maintain those sync settings. For instance, Item C and Item Dthat were created under the different sync settings illustrated inExample 3 and 4 are not cross-pollinated.

Example 6 shows removing the home PC sync source. According to oneembodiment, any items created on the device that is removed are alsoremoved from the other sync devices when that is the only instance ofthe item. In this example, Item D is removed from the device, but Item Bis not removed since it was synced with the Work PC also.

FIG. 5 illustrates an exemplary sync table architecture, in accordancewith aspects of the invention. According to one embodiment, SQL-CE isused to maintain the synchronization states.

A DB File (510) contains a single table for each data type tosynchronize. This example illustrates synchronizing Contacts, Calendar,and Tasks. Since changes to an item can happen in many tables, theLastModified field (540) associated with the item is updated wheneverthe item is edited. This helps to ensure that all changes are noted andsynchronized. Changes to an item in the Item table, the CategoryAssociations table, or any other relevant table triggers an update ofthe LastModified field. According to one embodiment, the value is set tothe current Device Date and Time. This flag is touched upon each updateto an item helping to ensure that the SQL-CE Change Tracking systemproperly tracks any item changes. As illustrated, a last modified columnis added to the Contacts (524), Calendar (520) & Tasks tables (522). Thelast modified column is updated every time an item is changed.

The following is an exemplary description of the items within thetables. Category Constant Value DataSourceType alAirSyncServer 1alAirSyncDesktop 2 Data Sources - Data to track for each Data SourceDataSourceID PK, GUID Unique Identifier per Data Source DataSourceTypelong Indicates what type of Data Source this is. Used to track itscapabilities FriendlyName nvarchar Name for Data Source, used by theApps to Identify stores NetworkAddress nvarchar Address for Data Source.Value is set depending on Data Source Type

According to one embodiment of the invention, custom properties (SyncCustom Props 5560) for each data source are stored in the Registry.These custom properties include the details that the sync engine tracks.According to one embodiment, the server keeps track of Username,Password, and Domain, Rules. A desktop source keeps track of Username,Password (optional), Domain, Rules, and Machine Name.

The following is a list of exemplary data source application programinterfaces, according to aspects of the present invention. Data SourceAPIS Functionality Description Create Data Source Parameters: HRESULTCreateDataSource([in] UINT DataSourceType cProps, [in] CEPROPVALS*rgVals, [out] FriendlyName GUID *pDataSourceID); NetworkAddressExchangeServer The new Data Source is created and if successful the newDataSourceID is passed back in the OUT parameter. The friendly namepassed in is unique. If the FriendlyName requested already exists anerror may be returned to the calling function. Edit Data Source HRESULTGetDataSourceProps([in] GUID Pass in DataSourceID to indicateDateSourceID, [in] UINT cProps, [in] which Data Source to update. All ofCEPROPVALS* rgVals); the properties set in the create HRESULTSetDataSourceProps([in] GUID operation can be edited. DateSourceID, [in]UINT cProps, [in] Editing any of these fields does not CEPROPVALS*rgVals); require a reset of the sync key Delete Data Source HRESULTDeleteDataSource([in] GUID Delete the requested Data Source andDateSourceID); delete the column for this Data Source from the Tables.If an item was syncing but is now no longer connected to a sync source,delete the Item from the table. Get Data Sources HRESULTEnumDataSourceFirst([out] Retrieve and enumerate through the HANDLE*phEnum, [out] GUID list of Data Sources *pDataSourceID); HRESULTEnumDataSourceNext([in] HANDLE hEnum, [out] GUID *pDataSourceID);Set/Retrieve Sync To Settings for Item struct SyncDataSource {  GUIDDataSourceID;  BOOL fSyncing; } HRESULT GetDataSourceForItem([in] GUIDGetDataSourceForItem itemID, [in] GUID itemType, [out] For new itemsthis API is called to SyncDataSource **ppSDS); determine the list ofData Sources the HRESULT SetDataSourceForItem([in] GUID itemType cansync to and the default itemID, [in] GUID itemType, [in] values (whichData Sources a new item SyncDataSource *pSDS); should sync to bydefault) For existing items this API is called to determine the list ofvalid Data Sources the item can sync to and the current sync values(where the item currently is syncing to) Use this API to set the Sync Tovalues for the itemID specified. SetDataSourceForItem This functionresponds to several situations 1: New Item - set the pending flags 2:Edit with same values - Do nothing 3: Edit with new values - Mark forpending delete or pending where appropriateDifferentiation between Hard & Soft Deletes

FIG. 6 illustrates a soft delete and a hard delete, in accordance withaspects of the invention. According to one embodiment, the sync protocolsends down a delete for an item if it falls out of filter (is no longersynchronized) or if it is physically deleted. According to oneembodiment, filter setting for the items cross-pollinating aredevice-wide settings. Because of possible data loss with the propagationof out-of-filter deletes across cross-pollinating sources, a Hard Deletecommand is used to aid in differentiating between a Soft and Harddelete.

The term “Hard Delete” refers to physically deleting the item from eachof the stores. The hard delete propagates across all cross-pollinatingsources. The term “Soft Delete” refers to the fact that the item hasgone out of filter. The soft delete removes the item from the device,but does not propagate the delete to any other source.

If a version of the synchronization protocol does not supportsoft-deletes then when a delete command is received, the device willonly delete the item from its store. In other words, the delete does notcross-pollinate. Since it is possible that an Item can end up in filtersince the last sync, Soft-Deletes occurs at the end of the Sync session.

For example, item 610 is soft-deleted from Server then the item will bedeleted off of the Device, but not off of the Home PC, as illustrated bydeletions 620. If on the other hand, the item is hard-deleted off of thework PC then Item 610 is deleted off of the device and the home PC, asillustrated by deletion 625. Delete commands are ignored when a devicereceives a delete command for an item that does not exist.

Duplicate Detection

FIG. 7 illustrates processing a command to add an item to the device, inaccordance with aspects of the invention. Before an item is added to adevice, a duplicate detection check is completed. Performing a duplicatedetection check helps to ensure that duplicates are not created on thedifferent devices that are being cross-pollinated. According to oneembodiment, the duplicate detection is based upon item propertycomparison and the duplicate detection code is implemented on the device(such as device 305 illustrated in FIG. 3).

At block 710, the device receives an add command from the data sourcebeing synchronized. Moving to block 715, the device calculates a hashvalue for the item to be added and searches a store for any other itemsthat have the same hash value. The hash value is used to uniquelyidentify the item. Other ways of uniquely identifying the item may beused. Moving to decision block 720, a determination is made as towhether the device is cross-pollinating.

If the hash is located at decision block 725, then the device willconsider the item a duplicate and move to decision block 735. When thesync hash is not found the process moves to block 730, where the item isadded to the device and a sync pending bit is set. At decision block735, if the found item is currently syncing with this data source thenthe item is created and a sync pending field is set at block 730.According to one embodiment, the Device will not consider anything to bea duplicate if the item on the device with the matching Sync Hash isalready syncing with the source.

When the item is not currently synchronizing with the data source thenthe process moves to block 740, where the item is detected as aduplicate. At this point, the device will keep the version it alreadyhas and simply add the ID for the new item to the existing record.

FIG. 8 illustrates an exemplary duplicate detection scenario, inaccordance with aspects of the present invention. Generally, when anitem is added to the device, a SyncHash (810) is calculated on a subsetof the items properties. Item A has a sync has value of HASHIO (815).When the device receives items to add, the device compares the SyncHashof the new item to the existing items, allowing the device to detectduplicates.

Referring to step 1, Item A has already been synced to the device fromServer 1. At this point, Item A is on Server 1 and the Device with aSyncHash value of HASH101. At step 2, a user copies Item A from theirdevice to Server1 creating Item B on device Server1. Item B has the sameSyncHash value as Item A. When the device syncs with the server at step3 Item B will be created on the device since it is already synching withthe server.

Calculating the Hash

Two levels of property level matching are employed in calculating theSync Hash.

Exact data comparison (primary keyset): A set of fields is defined asthe primary properties that are compared to consider the item aduplicate. This set of fields may be different for each data type. Theset of fields chosen should be able to be adapted in the code withoutmajor code change. This could include listing the fields in a headerfile so that the algorithms can be tuned during the test process.

Property Existence (secondary keyset): A larger set of fields, almostcompletely inclusive, is used to check for the simple existence of datain those properties. This helps to ensure that if a field is set in oneitem and is blank in another, then even if there primary key's match,the items will not be considered duplicates of one another.

Storing/Updating the Hash

When an item is first synced, the SyncHash is calculated and stored onthe item. The SyncHash value is updated when an edit occurs on an itemalready synchronized. The following is an exemplary primary andsecondary keysets for contacts, calendar, and tasks, according to oneembodiment of the invention. Other properties are used to create theprimary and secondary keysets for other items to be synchronized.Properties Contacts Sync Hash Algorithm Primary Keyset FirstName (Exactdata comparison) LastName Last 4 chars of HomePhoneNumber Last 4 charsof BusinessPhoneNumber (If less than 4 digits use whatever exists)Secondary Keyset Anniversary, AssistantName, AssistnamePhoneNumber,(Property Existance) Birthday, Body, Business2PhoneNumber, BusinessCity,BusinessCountry, BusinessPostalCode, BusinessState BusinessStreet,BusinessFaxNumber, CarPhoneNumber, CompanyName, Department,Email1Address, Email2Address, Email3Address, FileAs, Home2PhoneNumber,HomeCity, HomeCountry, HomePostalCode, HomeState, HomeStreetmHomeFaxNumber, JobTitle, MiddleName, MobilePhoneNumber, OfficeLocation,OtherCity, OtherCountry, OtherPostalCode OtherState, OtherStreet,PagerNumber, RadioPhoneNumber, Spouse, Suffix, Title, WebPage,YomiCompanyName, YomiFirstName, YomiLastName Calendar SyncHash AlgorithmPrimary Keyset UID, StartTime, Location, Subject (Exact data comparison)Secondary Keyset AllDayEvent, Email, Name, DtStamp, EndTime, Deleted,(Property Existance) ExceptionStartTime, MeetingStatus, OrganizerEmail,OrganizerName, Recurrence, Type, Until, Occurrences, Interval,DayOfWeek, DayOfMonth, WeekOfMonth, MonthOfYear, Reminder Tasks SyncHashAlgorithm Primary Keyset Subject, DueDate, Categories (Exact datacomparison) Secondary Keyset StartDate, CompletedDate, Importance,IsComplete, (Property Existance) IsRecurring, Sensitivity, ReminderSet,ReminderTime, Body

If an Item is marked for cross-pollination, the data available on thedevice will cross-pollinate to the other Data Sources. Truncatedversions of an item may cross-pollinate because of device limitations.According to one embodiment, the text [Message Truncated] is added tothe end of the Notes field when truncation occurs. Users will thereforebe aware that they do not have the complete original copy The syncengine on the device first requests all Adds from the Data Source. Itthen sends up to the Data Source all Adds that still remain (theduplicated adds have been marked and therefore will not be issued).

According to one embodiment, an Item on the Device tracks threeproperties. The ServerID values and SyncHash will be stored as customproperties on each Item. Description Property ItemID This is used toidentify the item ServerID1 . . . N This is the ID that identifies theitem at the Server/ Desktop The Item can have multiple Server IDs storedas custom properties in the Item. SyncHash This is the sync hash valueused to detect duplicates. This value is calculated/re-calculated eachchange The ServerID property has four states: Sync State Sync PendingItem is on Device and not yet synced to the target Data Source. The Itemis created on the Data Source upon next sync. Valid ServerID The ItemsServerID is stored to allow for proper mapping with the Data SourcePending Delete The Item has synced in the past to this Data Source butthe user has requested that it no longer sync there. On the next syncdelete the item from the Data Source and clear the property Not SyncingThe Item is not syncing with this Data Source

FIG. 9 shows processing an add command for a duplicate of an existingitem on the Device, in accordance with aspects of the present invention.For an item that is considered a duplicate, the process moves to block910 where the add command is converted to a change command. Instead ofcopying the entire item to the device, the item is updated. At block920, the property list is compared with the known schema. Flowing toblock 930, explicit deletes are added to the change command for theknown properties that were not provided. Block, 940 illustrates theupdated command. At block 950, the change command is processed.

Cross-Pollination across Different Sync Versions

Property level change tracking is implemented in order to aid insupporting multiple synchronization protocol versions cross-pollinating,and minimize unnecessary writes. Each sync provider is responsible forknowing the property set it syncs and for only initiating a sync when achange occurs in properties that it cares about. Because a sync provideronly changes properties that it is aware of, it is possible that an itemon the device will contain a merged set of properties, some propertiesfrom the a v1 server and the other properties that only the v3 serversyncs.

FIG. 10 illustrates cross-pollinating a v1 and v3 server, in accordancewith aspects of the invention. Different versions of sync protocolssupport different properties. In the example illustrated, the V1protocol supports properties A and B, whereas the V3 protocol supportsproperties A, B, and Z.

Initially, the Device has not been synchronized with the V1 Server orthe V3 server. At 910, the device first syncs with the V1 server andreceives items A and B. Next, at 920, the device syncs with the V3server. Items A and B are detected as duplicates and items A, B, and Zare synchronized to the Device. At 930, when the device syncs with theV1 server again no synchronization occurs since item Z is the onlychange and it is not supported by the V1 server.

FIG. 11 shows an exemplary synchronization scenario, in accordance withaspects of the present invention. Step 1110 illustrates that Item A haspreviously cross-pollinated with the Home PC and the Work Server. At1120, Item A is edited creating version 2 (v2) of Item A. The Devicesyncs with the work server at 1130 where version 2 is synced to thedevice. Next, at block 1140 the device syncs with the Home PC. Since theDevice is set to server wins Item A (version 1) is now on the device.When the device syncs with the Work Server again there is no conflictand Item A—version 1 is now on the work server (1150).

FIG. 12 shows an exemplary synchronization scenario, in accordance withaspects of the present invention. Step 1210 illustrates that Item A haspreviously cross-pollinated with the Home PC and the Work Server. At1220, it is identified that the sync key has a value of zero at the workserver. The user is cross-pollinating so the Work Server ID is deleted(1224) at block 1230. Moving to block 1240, The synchronization isstarted from scratch and the device receives an add command requestingto add Item A to the device. The item is detected as a duplicate, andthe item from the Home PC is kept. The work server ID is added to theItem tag.

Creating a Data Source

FIG. 13 illustrates Data Source Creation, in accordance with aspects ofthe present invention. After a start block, the process moves to block1310, where account information for the new data source is obtained.Flowing to block 1320, a request is made to register a new data sourcewith the system. At block 1330, the data source type is set to a typeassociated with the data source. According to one embodiment, the datasource type relates to the type of device, i.e. DesktopSync andServerSync. Next, at block 1340, the machine name is recorded. Thishelps to allow the device the ability to reconnect to the desktop (inmost cases) if the Desktop Sync Information is lost. The process thenmoves to an end block and returns to processing other actions.

Removing a Data Source

FIG. 14 shows a process for removing a data source, in accordance withaspects of the present invention. Deleting a Data Source deletes theData Source and all of the items that the Data Source was syncing. If anItem was syncing, or is pending sync, with more than one Data Source,then the item will not be deleted.

After a start block, the process moves to block 1410 where adetermination is made as to how many sources the device is syncing with.Moving to decision block 1420, when there is only one data source, theprocess moves to block 1430 where the items being synced with thedeleted data source are removed from the device. When there is more thanone device, the process moves to block 1440 where the noncross-pollinated items on the device are removed. Transitioning to block1450, the source's ID that was deleted is removed from the device.According to one embodiment, the custom columns for this Data Source areremoved from the application tables. According to one embodiment, awarning message is provided to the user before removing any data.

The following is an example to further clarify. Suppose, a device issyncing its Contacts, and Calendar with a first source and the device issyncing Calendar and Tasks with a second source. The user then deletesthe first source. As a result of removing the first source, all of thecontacts are purged from the device. The calendar items and tasks areleft on the device and the IDs for the first source are removed.

Reconciling Data Source Information that is Out of Sync

FIG. 15 illustrates reconciling data source information that is out ofsync, in accordance with aspects of the invention.

The following examples will be used to illustrate. A Data Source (WorkPC) exists on the device that the Work PC is no longer aware of. Thiscan occur for many reasons. For example, it can occur if the user has toreinstall the synchronization program or rebuild the machine. When thedevice connects to the desktop, the desktop notices that the devicealready has a data source setup to sync with it (1510). This isdetermined by comparing the network machine name of the Data Source onthe Device with the name of the Work PC. The existing Desktop Source isdeleted and a new one is created. The device may

A Data Source exists on the Desktop that the Device is no longer awareof. This can occur, for example, if the device cold boots. By comparingthe DeviceID stored on the Desktop for the Data Source with the device'sDevicelD it can be determined that the device used to sync with thedesktop and a determination is made as to whether the device should beset up again to sync with the desktop. If the user says ‘yes’, a newdata source iscreated for the user.

The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theinvention. Since many embodiments of the invention can be made withoutdeparting from the spirit and scope of the invention, the inventionresides in the claims hereinafter appended.

1. A method for synchronizing a device with data sources and allowingcross-pollination of the data sources, comprising: creating a first datasource and a second data source; connecting the device to a first datasource; synchronizing the device with the first source; connecting thedevice to a second source; and synchronizing the device with the secondsource, wherein the device may be used to cross-pollinate between thefirst data source and the second data source.
 2. The method of claim 1,further comprising performing a duplicate detection check to determinewhen an item has already been synchronized.
 3. The method of claim 2,wherein performing the duplicate detection check further comprisesperforming a property comparison.
 4. The method of claim 2, whereinperforming the duplicate detection check further comprises calculating async hash value.
 5. The method of claim 2, further comprising updatingthe item when the item has already been synchronized.
 6. The method ofclaim 1, further comprising receiving a delete command and performingthe delete command, wherein the delete command is selected from a softdelete and a hard delete.
 7. The method of claim 2, further comprisingrestricting cross-pollination between the data sources.
 8. The method ofclaim 2, wherein creating the first data source and the second datasource further comprises indicating a data source type and storing anidentifier associated with each of the first data source and the seconddata source.
 9. The method of claim 2, wherein synchronizing the devicewith the first data source may use a first synchronization protocol andsynchronizing the device with the second protocol may use a secondsynchronization protocol.
 10. A computer-readable medium forcross-pollinating data sources, comprising: creating at least two datasources to synchronize with a device; synchronizing the device with theat least two data sources; and cross-pollinating data between the atleast two data sources.
 11. The computer-readable medium of claim 10,further comprising performing a duplicate detection check to determinewhen an item has already been synchronized.
 12. The computer-readablemedium of claim 11, wherein performing the duplicate detection checkfurther comprises calculating a sync hash value.
 13. Thecomputer-readable medium of claim 11, further comprising receiving adelete command and performing the delete command, wherein the deletecommand is selected from a soft delete and a hard delete.
 14. Thecomputer-readable medium of claim 13, further comprising restrictingcross-pollination between the data sources.
 15. The computer-readablemedium of claim 13, wherein creating the at least two data sourcesfurther comprises indicating a data source type and storing anidentifier associated with each of the at least two data sources. 16.The computer-readable medium of claim 13, wherein synchronizing thedevice with the at least two data sources may use more than onesynchronization protocol.
 17. A system for cross-pollinating datasources, comprising: at least two data sources that may cross-pollinateeach other; a device that is configured to act a shuttle between the atleast two data sources to cross-pollinate, and that is configured tosynchronize with the at least two data sources.
 18. The system of claim17, wherein the device is further configured to perform a duplicatedetection check to determine when an item has already been synchronized.19. The system of claim 18, wherein performing the duplicate detectioncheck further comprises calculating a sync hash value.
 20. The system ofclaim 18, wherein the device is configured to process a soft deletecommand and a hard delete command.
 21. The system of claim 20, whereinthe device is further configured to restrict cross-pollination betweenthe at least two data sources.
 22. The system of claim 21, whereinsynchronizing the device with the at least two data sources may use morethan one synchronization protocol.